Cream of the Crop 25

home *** CD-ROM | disk | FTP | other *** search

/ Cream of the Crop 25 / Cream of the Crop 25.iso / bbs / fdapxfaq.zip / FDAPXW.FAQ

Wrap

Text File | 1997-03-26 | 42KB | 1,128 lines

FrontDoor APX/w - Frequently Asked Questions ============================================ Version: 2, 26 March 1997 Author: Mats Wallin, Definite Solutions This is the official FAQ for FrontDoor APX/w from Definite Solutions, the client (point) package for the Windows operating system. Current FrontDoor APX version: 1.12, released 26 March 1997 Table of contents ----------------- 1. Introduction 1.1 New versions 1.2 Feedback 1.3 Copyright 2. General information 2.1 FrontDoor APX - what is it? 2.2 Distributors of the commercial version 3. Program usage 3.1 Crash messages / File requests 3.2 File attaches 3.3 Copy your unread messages to a specific folder 3.4 Using a LAN to connect to the server 3.5 Message base maintenance 3.6 Message threads / Message linking 3.7 More than one server 3.8 Events / Calling the server at specific times 3.9 Fonts 4. Other questions 4.1 Using a nodelist 4.2 File transfer protocols 4.3 Message base 4.4 DOS version 4.5 Uninstall 4.6 Mail not compressed 4.7 'Unsent' message marked as 'sent' 5. Examples and suggestions 5.1 Keyboard macros 6. Troubleshooting guide 6.1 Error installing FrontDoor APX 6.2 Problem connecting to a server 6.3 Rescan of a folder does not work 6.4 Error: Invalid client address 6.5 Messages to you not displayed differently in the survey 6.6 Error: Unable to open C:\FDAPX\MSG\FOLDER.APX: Path not found 7. Information to the operator of a server 7.1 Information that a FrontDoor APX user needs from you 7.2 Information that you might want to know 7.3 Using FrontDoor APX on a LAN 7.4 Pre-configure an archive for your clients (points) 1. Introduction --------------- This document is intended to help answer many of the questions frequently asked by users of FrontDoor APX/w. 1.1 New versions ---------------------------------- New versions of FrontDoor APX and of this document is available from the following locations: World Wide Web: http://www.defsol.se FTP: ftp.ttown.com (/pub/defsol/def) FidoNet: 2:201/329 2:201/330 Bulletin Board, BBS: +46 8 55630102 (X.75 / V.34) +46 8 55630103 (V.34+ / HST / X.75) 1.2 Feedback ------------- All feedback regarding this FAQ, as well as the program, including positive and negative comments, suggestions on how to improve them, etc., is very much appreciated. Please send feedback to: Mats Wallin, 2:201/329 mw@defsol.se 1.3 Copyright of this document ------------------------------- This FAQ is copyrighted 1997, Mats Wallin. It may be copied and distributed freely as long as this copyright and information about the author remains. Translations to other languages is allowed as long as the translator includes information about the persons involved in the translation. 2. General information ---------------------- 2.1 FrontDoor APX - what is it? -------------------------------- Q: What is FrontDoor APX/w? A: FrontDoor APX/w is a integrated program that contains all functionality that a client (point) should need. It contains, among other things, an EMSI compatible mailer, using the ZModem file transfer protocol, a fully-fledged message editor, functions to import and export messages, etc. The program runs under Windows 3.1x, Windows 95 and Windows NT. It can also be used under OS/2 running in a WinOS2 session. Q: Can FrontDoor APX answer incoming calls? A: The commercial version of FrontDoor APX can answer incoming calls (the shareware version cannot). However, it cannot be used as a front-end for a BBS, and it can not be used as a standard mailer. It cannot be used as a server either. Even if it does answer incoming calls, messages it receives during these sessions will never be sent to another system; it is always imported into FrontDoor APX's message base. 2.2 Inquires about the commercial version ------------------------------------------ For information about the commercial version of FrontDoor APX, please contact: Europe: ComDas GmbH attn. Mr. Joerg Dassler Rathgeberstrasse 43c D-91074 Herzogenaurach Germany Telephone: +49 9132 78160 Fax: +49 9132 781615 BBS: +49 9132 781621 FidoNet: Joerg Dassler, 2:2490/1510 Australia and New Zealand: Aquarius Communications PO Box 4772 Sydney NSW 2001 Australia Telephone: +61 41 1174 014 Fax/BBS: +61 2 9948 9122 Internet: sales@aquarius.com.au FidoNet: Glen Harvy, 3:714/930 USA and Canada: Online Communications, Inc. attn. Mr. James Smith 22 State Street Bangor Maine 04401 USA Telephone: +1 207 941 1110 Fax: +1 207 990 2293 BBS: +1 207 990 3511 Internet: james@ocinet.com FidoNet: James Smith, 1:132/300 3. Program usage ---------------- 3.1 Crash messages / File requests ----------------------------------- Q: How do I send a message crash to a system that is not my server (boss)? Q: How can I make a file request from someone that is not my server (boss)? A: This is not possible in the current version. The main reason for this limitation is that FrontDoor APX does not have a nodelist, and therefore does not have access to phone numbers of other system. The plan is to include this possibility in the 1.20 version of FrontDoor APX. 3.2 File attaches ------------------ Q: I want to attach a file to a message, how can I do this? A: It is not possible to attach a file to a message in FrontDoor APX. However, you can easily send files to another user. Use the Send command in the Services menu (or the File Queue command in the same menu) to select the files you want to send, and the recipients of the files. The files you send are always sent via the server. 3.3 Copy your unread messages to a specific folder --------------------------------------------------- Q: I want all messages that are addressed to me to be copied to another folder. How do I do that? Q: How can I easily find all messages that are to me? A: FrontDoor APX has the possibility to create a copy of all conference messages that are addressed to you in another folder. You can use this to easily find and read all your messages, when you do not have the time to read all other messages. To use this function, follow these steps: 1) Make sure that the User Interface Level is set to Advanced. (To do this, select the System command in the Options menu.) 2) Create a new folder. It is recommended that this folder is configured as a Local folder, and that the Folder status is set to ReadOnly. 3) If you want all conferences messages to be copied to this folder, edit the 'All folders' group, and select the Advanced page. Click on the Personal To button. Select the new folder, created in step 2 above, from the list. If you only want messages in certain folders to be copied to the new folder, edit another group than the 'All folders' group, or each folder. When you reply to a message in this folder, the reply will automatically be stored in the correct folder. 3.4 Using a LAN to connect to the server ----------------------------------------- Q: I cannot get FrontDoor APX to connect to my *** server via a LAN? A: FrontDoor APX is only able to connect with a FrontDoor server via a LAN. No other mailers are currently supported. However, you should be able to connect to any other mailer via a modem, as long as the mailer supports EMSI. 3.5 Message base maintenance ----------------------------- Q: Does FrontDoor APX remove old messages automatically, or should I do this manually? A: FrontDoor APX automatically maintains your message base every third day (by default). When it runs maintenance, it will delete old messages and pack the message base to free disk space. By default, a message is kept in the message base for 30 days from the day it arrived. (An exception to this rule is that messages in the 'Private mail' folder is never deleted automatically. If the User Interface Level is set to Intermediate or Advanced, it is possible to define the number of days messages should be kept for each folder, and also the maximum number of messages in each folder. To configure these settings, select the Folder command in the Options menu and then select a folder to edit. Q: I have FrontDoor APX running all the time, but it never runs the automatic maintenance. A: FrontDoor APX does only check if it should run the automatic maintenance each time you start the program. To have it run the maintenance automatically, you have to quit and restart FrontDoor APX at least once each day. If you do not wish to do that, you can instead run maintenance manually. To do this, close all windows that display messages. Then choose Maintenance from the Service menu. 3.6 Message threads / Message linking -------------------------------------- Q: FrontDoor APX does not seem to link messages that have the same subject. A: That is correct. FrontDoor APX uses real reply linking instead of the subject line linking some other programs uses. Real reply linking uses two control information lines in the messages, the MSGID and REPLY lines. Real reply linking has the great advantage that you directly can jump to the original message, or to the first reply of the current message. Q: I can't follow the reply links with the ... keys that my other editor is using. A: FrontDoor APX uses the following keys when following a reply link: / Jumps to the message that the current message is a reply to. * Jumps to the first reply of the current message. + Jumps to the next message that is a reply to the same message as this message. - Jumps to the previous message that is a reply to the same message as this message. There are also buttons in the toolbar that can be used to follow the reply links. 3.7 More than one server ------------------------- Q: Can I configure more than one server with FrontDoor APX? A: Yes, it is possible to do this. To define more than one server, follow these steps: 1) Make sure that the User Interface Level is set to Intermediate or Advanced. (To do this, select the System command in the Options menu.) 2) Select the Server command in the Options menu. 3) If a list of servers are displayed, click on the Add button. If information about a single server is displayed, click on the New Server button. 4) Define the new server as usual. Q: My server has more than one address, and I have more than one client (point) address of his system. How can I tell FrontDoor APX that all these servers are the same system? A: There is no need to tell FrontDoor APX this. When you call the server, FrontDoor APX checks all addresses that the server presents, and understands which addresses belong to this system. 3.8 Events / Calling the server at specific times -------------------------------------------------- Q: Can I configure FrontDoor APX to call the server automatically at a specific time? A: It is not possible to configure this in FrontDoor APX itself, but it is very easy to do it with an external program. Many different programs that allows this exist. For instance, the Microsoft Plus package for Windows 95 contains a program called System Agent that allows you to run another program at a certain time. Many similar programs also exist for Windows 3.x, one example is CRON18.*, which is available from (among other places) www.shareware.com, and also from our BBS (see above). To have these programs execute FrontDoor APX so that it automatically calls the server to pickup mail, use the following command line: C:\FDAPX\FDAPX.EXE /CALL (If FrontDoor APX is installed in another directory then C:\FDAPX, insert the correct directory instead). If you have more than one server defined in FrontDoor APX, the above command line will call all defined servers. If you only want to call a certain server, use the following command line: C:\FDAPX\FDAPX.EXE /CALL:1 which will call the first defined server. Replace 1 with another number to have it call another server. (Version 1.10 of FrontDoor APX did not allow you to specify which server to call with the /CALL:1 switch. If you need to do this, make sure you upgrade to the latest version). 3.9 Fonts ---------- Q: I have used the Font command in the options menu to define another font, but every time I switch to another folder, the font is reset to another font. A: The Font command in the Options menu is only intended for temporary changes of fonts. As soon as you switch to another folder, the font is reset to the default font. There are three different default fonts that can be defined. 1) The default normal font. This font is used in all folders for which you haven't defined a folder specific font, and for all messages that should not be displayed with a non-proportional (fixed) font. This is in most cases the font that is used most often. To define this font, select the Define Fonts command in the Options menu, and then select Default Font. After selecting a new default font, it will be used the next time you switch to another folder. 2) The default fixed font. This font is used in all folders that you have configured to use a fixed font, for all messages that should be displayed with a non-proportional font, and when you select the Fixed command in the Options menu. To define this font, select the Define Fonts command in the Options menu, and then select Fixed Font. 3) The default folder font. This font is only used for the folder for which it is defined. To define this font, edit the folder settings for the folder (select Folder in the Options menu, select a folder, and then click Edit). Select the Advanced property page, and click on the Font button. The User Interface Level must be set to Advanced to be able to configure a default folder font. 4. Other questions ------------------ 4.1 Using a nodelist --------------------- Q: Can I use a nodelist as the address book? A: It is possible to convert a nodelist to the address book format that FrontDoor APX uses. A program called NL2APX is included together with FrontDoor APX, and is used when you want to convert the nodelist. All you have to do to convert the nodelist with NL2APX, is to execute NL2APX with the name of the nodelist as a parameter. NL2APX will then create the file ABOOKPUB.TXT in the current directory. Example: NL2APX NODELIST.320 If you have more than one nodelist, it is possible to convert all of them at the same time, just specify all nodelists on the command line. If you also are using FrontDoor, and want to convert all nodelists you use with it, use the following command: NL2APX C:\FD\NL\NODELIST.* C:\FD\NL\FDNET.PVT C:\FD\NL\FDPOINT.PVT (The command line above assumed that the nodelist directory specified in FDSETUP is C:\FD\NL). Version 1.12 of NL2APX also adds the possibility to specify a default zone. This is useful when a nodelist that should be included does not contain any zone information. To use this possibility, specify the /ZONE=<zone> switch when running NL2APX, for instance: NL2APX /zone=10 C:\FD\NL\NODELIST.* C:\FD\NL\FDNET.PVT 4.2 File transfer protocols ---------------------------- Q: Does FrontDoor APX support Hydra? A: No, it does not. Hydra is a very nice file transfer protocol for systems that transfer much data in both directions. However, most client (point) systems does not, and ZModem is in these situations just as good as Hydra. Future versions of FrontDoor APX might add support for Hydra, but we can not promise when this will happen. 4.3 Message base ----------------- Q: Which message base format does FrontDoor APX use? Q: Can FrontDoor APX use a JAM message base? A: FrontDoor APX uses a proprietary message base format, which is designed to be very effective for a client (point) system. Since all utilities that are needed to maintain the message base, including a tosser, scanner, message base maintenance, and the editor, are included in FrontDoor APX, the need to use a message base format such as Hudson or JAM does not exist. The FrontDoor APX message base is in some aspects based on the JAM message base. It does for instance use real reply threads. Two messages are not linked to each other, just because they happen to have the same subject. The messages are only linked if one of them is a reply to the other one, or if both of them are reply to the same third message. 4.4 DOS version ---------------- Q: FrontDoor APX seems very nice, but is there a DOS version available? A: There is a DOS version of FrontDoor APX. As of this date, the DOS version does not exist as a shareware program, but this might change in the future. The DOS version can be bought from one of Definite Solutions' distributors and/or retailers. For a list of distributors, see 2.2 above. 4.5 Uninstall -------------- Q: How do I uninstall FrontDoor APX? A: I hope you do not want to uninstall FrontDoor APX, but if you need to do that, follow these steps: 1) Check if there are any files in the subdirectory FILE that you want to keep. This directory contains all files that you have received, so there might be some files that you should copy to another directory. 2) Remove the directory in which you installed FrontDoor APX (normally C:\FDAPX), including all files located in this directory. 3) Remove the FDAPX.INI file that is located in the Windows directory. 4) Remove the icon in Program Manager or the Start menu. In Windows 3.x, click once on the icon, and press Delete In Windows 95, right click on the Start button, and select Open. Select the folder where the icon is located, click once on the icon, and the press Delete. 5) FrontDoor APX does, if it didn't already exist, also install the file CTL3DV2.DLL to the WINDOWS\SYSTEM directory. This is a file that is used by many different programs, and it is provided by Microsoft. It is recommended that this file is not removed, since you do not know if any other program also is using this file. If you are completely sure that no other program is using it, you can remove it. 4.6 Mail not compressed ------------------------ Q: Why isn't the mail packets that FrontDoor APX sends to the server compressed? A: There are two main reasons for this: 1) Most clients do not write the amount of mail that it really makes any big difference to compress the files. 2) All modems sold today does have data compression built in (V.42bis), which means that the files are compressed on the fly when they are sent. It is true that for instance ZIP has a better compression ratio than V.42bis, but the difference in transfer time will not be noticeable. 4.7 'Unsent' message marked as 'sent' -------------------------------------- Q: If I write some messages and try to poll the server, but the poll fails the messages are still labeled as "Sent", is this a bug? A: No, messages are labeled as sent after they have been exported from the message base and packed into bundles to be sent to the server. This is irrespective of whether the bundle has already been sent to the server. If the poll fails, the bundle is retained for the next attempt until it is successfully transmitted to the server. 5. Examples and suggestions --------------------------- 5.1 Keyboard macros -------------------- To use the keyboard macros below, enter the data below exactly as specified in the Definition box of the Keyboard macros dialog. 1) [Top]Hello [CurDestFirstName], [Bottom] Sincerely yours, [YourFirstName] [YourLastName].[Top][Down][Down] (The macro above adds 'Hello <name>,' at the top of the message, 'Sincerely yours, <yourname>' at the bottom, and then moves the cursor to the first line of the message text. 6. Troubleshooting guide ------------------------ 6.1 Error installing FrontDoor APX ----------------------------------- Q: When attempting to install FrontDoor APX, I get the following message: Unable to copy file "abscomp.dll". File or directory access denied. A: The reason for this error is a bug in the installation program, which prevents it from copying files to a directory that contains 'extended DOS characters', such as A with two dots, O with two dots and A with a ring. The setup program creates the directory, but fails when attempting to copy the files. The only way to solve this problem is unfortunately to use another directory name, that does not contain one of these characters. 6.2 Problem connecting to a server ----------------------------------- Q: When I call my server (boss), the modem connects, but FrontDoor APX is not able to establish a session with the server. A: There can be a number of different reasons for this problem. The most common ones are listed below, together with possible solutions. 1) FrontDoor APX requires that the server supports a protocol that is called EMSI. All modern server programs does support this protocol today. Please check with the operator of your server if his system supports EMSI. Server programs that are known to not support EMSI includes: Old versions of BinkleyTerm McKennel SEAdog The solution to this problem is that the server updates the software to a later version that supports EMSI. 2) Most high speed modems (9600 BPS and above) can be configured to either use a constant data transfer speed between the computer and the modem, or a variable one. If the computer should be able to communicate with the modem, it has to be configured to use the same type of data transfer. To check if this is the problem, select the Modem command in the Options menu, and change the 'Modem BPS rate locked' setting to the other possible selection. Make a new attempt to call the server, to see if the problem has been solved. 3) When FrontDoor APX tries to connect with the server, it presents a password that you have defined in the server configuration. If this password is incorrect, the server will disconnect the call. To check if this might be the problem, contact the operator of the server and ask him to verify the password, and to check the logfile that his system has created to see if it has reported any password problems. 6.3 Rescan of a folder does not work ------------------------------------- Q: I have used the field 'Messages to rescan' when editing a folder, but I do not get any old messages from the server? A: The reason for this is in most cases one of the two following: 1) The server does not have any old messages in this conference in its own message base, and is therefor unable to send any messages to you. 2) The software used on the server does not support this function, or the type of request that FrontDoor APX uses. Software that is known to support this function includes: FastEcho More software will hopefully start to support the FSC-56 in the near future. Please ask the operator of your server to either switch to software that does, or to attempt to have the software updated. 6.4 Error: Invalid client address ---------------------------------- Q: When I try to add a new server, FrontDoor APX complains with a message that says 'Invalid client address'. A: This message was displayed in version 1.10 when you had entered one address in the server address field, and another address that is not a point address of the first one, in the client address field. For instance, 2:201/329 in server address field, and 2:201/330.1 in the client address field. Certain older programs did sometimes require a client to specify an administrative address instead of the actual server address. FrontDoor APX does instead handle this completely automatic, the client should have not to be bothered with the configuration of the server system. This means that when you specify the server address in FrontDoor APX, it should always be the first three numbers in your client address (i.e. 2:201/329 if your address is 2:201/329.1). However, due to many requests to change this, version 1.11 and later versions allow you to enter these types of addresses. FrontDoor APX warns you that the addresses you have specified might be incorrect, but allow you to use them if you choose to do that. 6.5 Messages to you not displayed differently in the survey ------------------------------------------------------------ Q: I've heard that messages to me that have not yet been read should be displayed differently in the message survey, but they are displayed the same way as all other messages. A: It is correct that unread messages to you should be displayed differently in the survey. If other messages are displayed with a non-bold font, these messages should be displayed with a bold font, and vice versa. If unread messages to you are displayed the same as all other messages, this is because the font you have chosen doesn't exist in both a bold and non-bold version. To correct this, define another default font. (To select another default font, see question 3.9). 6.6 Error: Unable to open C:\FDAPX\MSG\FOLDER.APX: Path not found ------------------------------------------------------------------ Q: When I've installed FrontDoor APX and attempts to start it the first time, FrontDoor APX first asks if it should create a new configuration file, and then displays 'Unable to open C:\FDAPX\MSG\FOLDER.APX: Path not found'. A: This error message is caused by a bug in version 1.11. It is always displayed the first time you start the program after installing FrontDoor APX. Just click OK to remove the message, and the program will continue normally. This bug was corrected in version 1.12 of FrontDoor APX. 7. Information to the operator of a server ----------------------------------------- 7.1 Information that a FrontDoor APX user needs from you --------------------------------------------------------- FrontDoor APX has been designed to make it very easy to setup and configure. However, there are still some information that a FrontDoor APX user needs to be able to configure and use the program: Required information: *) The address of the server (boss), i.e. your network address (for instance 2:201/329). *) The client (point) address, i.e. his address. The address can either be specified as the point number only (e.g. 11), or as a complete address (2:201/329.11). *) The session password to use. FrontDoor APX does not treat the session password case sensitive. FrontDoor APX can use different passwords as session password and packet password, but to make the configuration easier, we recommend that you use the same password for the session password, packet password, and also AreaFix password. *) The phone number to your system. FrontDoor APX can handle up to 10 phone numbers, so if you have more than one, please let the user know all of them. The phone numbers should be specified as they are dialed, i.e. in most cases without a country code. Optional information: *) FrontDoor APX can be configured so that it knows the address of an Internet gateway. When a gateway has been configured, the user does no longer have to type the address of the gateway each time he wants to send a message to an Internet address, all he has to do is to enter the Internet address as the recipient of the message. Because of this, if there is an Internet gateway that he is allowed to use, please let him know the name of the gateway program (in most cases UUCP), and its address. 7.2 Information that you might want to know -------------------------------------------- *) Compression formats FrontDoor APX supports ARCmail files compressed with the following programs: ARC 5.x ARJ 2.5x PAK 2.50 PKZIP 2.04 All compatible programs are also supported, such as Info-ZIP. Mail from a FrontDoor APX client is sent uncompressed. *) The FrontDoor APX address book FrontDoor APX does not use a standard nodelist directly. It does instead have an address book, which uses a different format. To help your clients to communicate with other clients of your system, or any other useful names and addresses, you might want to provide an address book to them. The address book should be called ABOOKPUB.TXT, and is a standard text file. Each entry in the address book should be specified on a line, in the following format: Lastname,Firstname,Address,System,Location The first three fields are required, the last two are optional. It is also possible to leave the second field empty. Spaces should NOT be replaced with underscores in this file. The file should be created with the same character set that Windows uses. FrontDoor APX is by default configured to use a new ABOOKPUB.TXT file that it receives from the server. This makes it possible to send it to all your clients each time any information has changed in the file, and FrontDoor APX will automatically start to use it at once. Before you do this however, please check with the client that he wants you to do this. He might have created his own ABOOKPUB.TXT file which would be replaced by your file. There is also a program called NL2APX.EXE including in the FrontDoor APX archive, which can be used to create an ABOOKPUB.TXT file from a standard nodelist. See 4.1 above. *) Fixed pitch fonts / Proportional fonts Since FrontDoor APX is a Windows program, it is able to use most of the fonts that are installed. Contrary to the fonts used in a DOS program, most fonts in Windows are proportional fonts, which means that the width of each character is different. This is not a problem in most messages, but when a message contains information that are in columns (for instance a table), it will often look incorrect with a proportional font. To prevent this problem, it is possible to add the NPD (Non Proportional Display) status to a message. If you know that you are sending messages that use columns, you might want to add the NPD status, if possible. To do this in a *.MSG or Hudson message, add a control information (kludge) line to the message that looks like this: @FLAGS NPD (@ should be replaced by a Ctrl+A character, ASCII 01h). In a JAM message base, there is a special header attribute for the NPD status. *) AreaFix messages When a FrontDoor APX user adds or removes a conference, he does not have to send the needed AreaFix messages manually. FrontDoor APX does this automatically for him. It is also able to send AreaFix messages that requests a list of available conferences, and a list of connected conferences. Since these functions are all handled internally by FrontDoor APX, it should in most cases not be necessary to instruct the user how to use AreaFix manually. *) Automatic creation of new conferences If there is a conference that you want the client to read, just connect the client to it. FrontDoor APX will automatically set everything up on the client when it receives the first message in an unknown conference. 7.3 Using FrontDoor APX on a LAN --------------------------------- FrontDoor APX can be configured to pickup mail over a LAN instead of via a modem, if a FrontDoor server is installed on the same LAN. When using this function, the operator of the FrontDoor server can configure a some settings that determines FrontDoor APX' behavior when used over a LAN. These settings should be located in a file with the name FDAPXLAN.CFG, and the file should be located in the directory that the FrontDoor APX client has configured as the FrontDoor directory, i.e. the directory where the SETUP.FD file is located. The FADPXLAN.CFG file is a standard text file, and can contain the following commands: SEMAPHORE <filename> This command specifies that FrontDoor APX should create the specified file after mail has been sent to the server. <filename> can be specified with or without a full path. If it is specified without a path, the file is created in the directory defined as Semaphore path in FrontDoor's configuration. FrontDoor APX attempts to determine the name of the semaphore it should create automatically from FrontDoor's configuration. However, with some FrontDoor versions in some situations, this is not possible. This setting is needed for all FrontDoor versions with a version lower than 2.11, and in some cases with versions 2.20 to 2.20c. It is not needed with versions after 2.20c (but can of course be used if so desired). HISTORYFILE <filename> FrontDoor APX by default updates FrontDoor's inbound history file with information about the call each time it connects to the server. The history file that FrontDoor APX uses is INBOUND.HIS in the system directory. If you want FrontDoor APX to use another history file, specify the name of the file with this command. <filename> can be specified with or without a full path. If it is specified without a path, the file is assumed to be located in FrontDoor's system directory. HISTORYTASK <task> FrontDoor version 2.20 and later stores the task number of the task that wrote a record to the history file. Since FrontDoor APX does not have a task number of its own, it does by default use the task number 0 when writing data to the history file. If you want FrontDoor APX to use another task number, specify a number between 0 and 255 with this command. NOHISTORY If you do not want FrontDoor APX to update the inbound history at all, use this command. If you do, any HISTORYFILE and HISTORYTASK commands will be ignored. 7.4 Pre-configure an archive for your clients (points) ------------------------------------------------------- Version 1.12 of FrontDoor APX adds a new installation function that makes it possible for you as the operator of a server to create a package that is pre-configured for clients of your system. You can for instance pre-configure your network address, the phone number to your system, etc. You can also create a number of folders that all your clients should have setup, for instance a conference for discussions between all your clients. It is even possible to pre-configure the name and network of the client, if you want to create a unique archive for each new client. To create a pre-configured archive, contact the company you bought the commercial version from, or if it is the shareware version that you are supplying to your clients, see the file SYSOP.TXT which is included in the shareware archive. // End of file "fdapxw.faq"